custom_build: build output goes in the directory for the req, not hard coded to Target
authorCody P Schafer <dev@codyps.com>
Fri, 5 Dec 2014 06:54:33 +0000 (01:54 -0500)
committerCody P Schafer <dev@codyps.com>
Fri, 5 Dec 2014 07:01:02 +0000 (02:01 -0500)
commita49305a1f3f875e42449c73078781d03954ed446
tree61eb523301df42c1f03a2a03fde623c4c3263352
parent70f5205dba9887d8dab07f72dbc507aa74b12c1f
custom_build: build output goes in the directory for the req, not hard coded to Target

This broke crossbuilds that had Host deps that used custom build
scripts, typically resulting in a failure to link (due to bad
relocations or symbols) the final executable or library.

Probably should have rustc check when generating an rlib that all the
containing objects have the appropriate arch.
src/cargo/ops/cargo_rustc/custom_build.rs